Clean up ClickToDial OAS validation warnings#96
Merged
YadingFang merged 1 commit intomainfrom May 7, 2026
Merged
Conversation
CAMARA Validation — PASS0 errors, 0 warnings, 0 hints | Profile: standard |
Signed-off-by: Yading Fang <fangyading@chinamobile.com>
3a45a71 to
ffd4cab
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What type of PR is this?
cleanup
What this PR does / why we need it:
This PR cleans up non-blocking CAMARA Validation warnings/hints in the ClickToDial OAS before the second r1.3 release candidate.
It addresses ClickToDial-owned OAS findings where the fix is local and does not change the API wire format:
EventTypeenum schema for ClickToDial event types;CallId;This follows the feedback in #94 to consider addressing the remaining warnings, including schema naming such as
sinkvsSink.Special notes for reviewers:
This PR intentionally does not modify:
release-plan.yaml;code/common/*;CHANGELOG.md;README.md;.github/workflows/*.The files under
code/common/*are kept synced with Commonalities r4.2 via.sync-manifest.yamland are not manually edited in this PR.This PR does not execute
/create-snapshotand does not start the release process.Any remaining findings located in
code/common/*should be handled centrally by Commonalities/tooling rather than locally in ClickToDial.Changelog input